MULTI-STEP AUTOMATED REFACTORING FOR CODE SMELL

Multi-step Automated Refactoring for Code Smell

In computer programming, code smell may origin of latent problems in source code. Detecting and resolving bad smells remain time intense for software engineers despite proposals on bad smell detecting and refactoring tools. Numerous code smells have been recognized yet the sequence in which the detection and resolution of different kinds of code smells are performed because software engineers d...

Framework for Automated Code Smell Correction in a BrownVeld Context

Developing code over a long period of time, in a heterogeneous team or under time pressure can lead to a lingering decay in readability, maintainability and thus reusability of software source code. In the past decades several approaches have been developed that tackle automatic detection of such code Waws, yet neglecting the automated correction as an essential and integrated step in the refac...

Minimizing Refactoring Effort through Prioritization of Classes based on Historical, Architectural and Code Smell Information

Improving a software system’s internal structure through regular refactoring is considered vital for its long and healthy life. However, despite its amenities, refactoring is not readily adopted by software development teams in industry mainly due to strict project deadlines and limited resources. Hence, they look for optimal refactoring recommendations that would incur minimal effort overhead ...

Refactoring Code to Increase

Refactoring Prolog Code

Refactoring is a popular technique from the OO-community to restructure code: it aims at improving software readability, maintainability and extensibility. In this paper we apply the ideas of refactoring to Prolog programs. We present a catalogue of refactorings adapted to or specificly developed for Prolog. We also discuss ViPReSS, our semi-automatic refactoring browser, and our experience wit...